Method and system for enabling merchants to share tokens

ABSTRACT

One embodiment of the present disclosure provides a system and associated processes for sharing cardholder data (CHD) between a merchant that utilizes tokenization and a second merchant that may or may not utilize tokenization. In one embodiment, the merchant, or an employee of the merchant, can use the system and associated processes to reacquire CHD from a tokenization provider system. In one embodiment, the merchant identifies to the tokenization provider system a desire to share CHD, which is associated with a token, with a second merchant. The merchant and/or the tokenization provider system can then invite the second merchant to register with the tokenization provider system. Once registered with the tokenization provider system, the second merchant can access any CHD that the merchant associated with the second merchant.

RELATED APPLICATION

This application in a continuation of U.S. application Ser. No.13/303,983, filed Nov. 23, 2011 and titled “METHOD AND SYSTEM FORENABLING MERCHANTS TO SHARE TOKENS,” which claims the benefit ofpriority under 35 U.S.C. §119(e) of U.S. Provisional Patent ApplicationNo. 61/476,194, filed on Apr. 15, 2011, and entitled “METHOD AND SYSTEMFOR SHARING TOKENS,” the disclosures of which are hereby incorporated byreference in their entirety.

BACKGROUND

Tokenization is a concept used in credit, debit, and gift cardprocessing systems to avoid storing cardholder data (CHD) such as creditand debit card numbers, pin numbers, expiration dates, card securitycodes, and the like at a merchant's location. For example, when amerchant initially accepts a credit card at a point-of-sale (POS)system, the CHD is encrypted and sent to a remote gateway system. Thegateway system requests authorization from a credit card processor,which obtains authorization from a bank that issued the card. Thegateway system receives the authorization from the credit card processorand provides a token to the merchant for storage along with theauthorization.

The token can be a globally unique, randomized, alphanumeric replacementfor the CHD. The merchant's POS system stores the token instead ofstoring the CHD. If the merchant needs to reauthorize a customer (forexample, to add a tip at a restaurant), the merchant sends the token tothe gateway system, which then sends the actual CHD to the processor.With tokenization, thieves cannot steal CHD from merchants because thetokens are stored in place of the actual CHD.

SUMMARY

Embodiments of the present disclosure relate to a system for sharingcardholder data (CHD). In some embodiments, the system includes atokenization system. The tokenization system may be configured toreceive CHD of a customer from a first merchant. The tokenization systemcan associate a token with the CHD in physical computer storage tothereby enable the token to be used to represent the CHD. Further, thetokenization system may be configured to electronically transmit thetoken to the first merchant so as to enable the first merchant toperform a first transaction for the customer without having to store theCHD. In some implementations, the system may include a token-accessgranting system that includes computer hardware. The token-accessgranting system may be configured to receive an indication from thefirst merchant that one or more of the token and the CHD are to beshared with a second merchant. In response to receiving the indication,the token-access granting system may be configured to authorize thesecond merchant to access one or more of the token and the CHD, therebyenabling the second merchant to perform a second transaction for thecustomer.

Additional embodiments of the present disclosure relate to a method forsharing a token associated with cardholder data (CHD) in a tokenizationprovider system to enable the sharing of cardholder data between users.In certain embodiments, the method may be performed by a token accesssystem implemented in a computing system that includes one or moreprocessors. The method may include generating a first set of words andassociating the first set of words with a token. The token may beassociated with CHD in a tokenization provider system. The method mayfurther include associating, in computer memory of the token accesssystem, the first set of words with a user. In addition, the method mayinclude providing access to the first set of words to the user. Themethod may also include receiving user authentication informationassociated with the user and receiving a second set of words from theuser. In some implementations, the method includes determining whetherthe user is authorized to use the token by at least authenticating theuser based, at least in part, on the user authentication information,and determining whether the second set of words matches the first set ofwords. In response to determining that the user is authorized to use thetoken, the method may include providing the user with electronic accessto the token.

Some embodiments of the present disclosure relate to a system forsharing cardholder data (CHD). This system may include a tokenacquisition system configured to provide CHD of a customer to atokenization provider system. Further, the token acquisition system maybe configured to receive electronically a token associated with the CHDso as to enable a first merchant associated with the token acquisitionsystem to perform a first transaction for the customer without having tostore the CHD. In some implementations, the system includes a tokensharing system configured to provide to the tokenization provider systeman indication that one or more of the token and the CHD are to be sharedwith a second merchant, thereby enabling the second merchant to performa second transaction for the customer.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers are re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate embodiments of the inventive subject matter described hereinand not to limit the scope thereof.

FIG. 1 illustrates an example embodiment of a token-sharing environment.

FIG. 2 illustrates a flow diagram for an example embodiment of a tokenprovisioning process.

FIG. 3 illustrates a flow diagram for an example embodiment of a processfor accessing cardholder data.

FIG. 4 illustrates a flow diagram for a second example embodiment of atoken provisioning process.

FIG. 5 illustrates a flow diagram for a second example embodiment of aprocess for accessing cardholder data.

FIG. 6 illustrates a flow diagram for an example flow of informationusing a tokenization provider system.

FIG. 7 illustrates an example embodiment of a user login interface.

FIG. 8 illustrates an example embodiment of a user registrationinterface.

FIG. 9 illustrates an example embodiment of a merchant selectioninterface.

FIG. 10 illustrates an example embodiment of a populated merchantselection interface.

FIG. 11 illustrates an example embodiment of a CHD access interface.

FIG. 12 illustrates an example of a CHD provisioning interface.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS Introduction

The security advantages of tokenization sometimes come at the expense offlexibility. Because a merchant that uses tokenization stores a tokeninstead of cardholder data (CHD), the merchant cannot share the CHD witha second merchant. This inability to share CHD can affect the merchant'sability to fully service his or her customers. For example, many qualityhotels will make restaurant reservations, order flowers, reserve theatretickets, and provide a number of additional services for guests thathelp differentiate these quality hotels from lesser quality hotels.However, without access to CHD, it becomes more difficult if notimpossible to provide guests with these aforementioned services.

Further, the lack of access to CHD by merchants that use third-partyservices, which take advantage of tokenization, can affect the abilityof some merchants to charge for cancelled reservations. For example, agolf course may work with a vacation reservation company to selltee-times to vacationers. If a vacationer fails to show up withoutproperly cancelling his or her reservation, the golf course may wish tocharge the vacationer a cancellation fee. However, if the vacationreservation company utilizes a tokenization service, the vacationreservation company will be unable to provide the golf course with theCHD.

Moreover, there are instances where a merchant may desire to reacquireCHD. For example, the merchant may want to process a transaction thatincludes interacting with a payment or credit card processor that is notsupported by the tokenization gateway, which handles transactions onbehalf of merchants that opt to use tokenization.

One embodiment of the present disclosure provides a system andassociated processes for sharing CHD between a merchant that usestokenization and a second merchant that may or may not use tokenization.In one embodiment, the merchant, or an employee of the merchant, can usethe system and associated processes to reacquire CHD from a tokenizationprovider system. In one embodiment, the merchant identifies to thetokenization provider system a desire to share CHD, which is associatedwith a token, with a second merchant. If the second merchant is notregistered with the tokenization provider system, the merchant and/orthe tokenization provider system can invite the second merchant toregister with the tokenization provider system. Once registered with thetokenization provider system, the second merchant can access any CHDthat the initial merchant associates with the second merchant.

In one embodiment, the second merchant identifies the token associatedwith the CHD to the tokenization provider system. If the merchant hasgiven the second merchant access to the token, then the tokenizationprovider system can provide the second merchant with the CHD. In oneembodiment, providing the CHD to the second merchant comprises thetokenization provider system performing a transaction using the CHD forthe second merchant. Advantageously, in some embodiments, thetokenization provider performing the transaction for the second merchantmaintains the security advantages gained from tokenization because thesecond merchant can use the CHD without the second merchant viewing theCHD and without a copy of the CHD being sent to the second merchant'slocation. In one embodiment, once the second merchant acquires the CHD,the second merchant can use the tokenization provider system, or thesecond merchant's tokenization provider system, to obtain a new tokenassociated with the CHD and the second merchant. The second merchant canthen take advantage of tokenization and avoid storing the CHD at thesecond merchant's location.

In one embodiment, providing the second merchant with access to thetoken and/or the CHD associated with the token comprises providing thesecond merchant with an authorization factor. This authorization factoris associated with one or more of the token, the CHD, and the secondmerchant. In one embodiment, to access the token and/or CHD, thetokenization provider system can request that the second merchantpresent the authorization factor as part of the user authenticationprocess. Advantageously, in some embodiments, use of the authorizationfactor prevents automated systems from accessing the token and/or CHD.Further, in some embodiments, use of the authorization factor increasesthe security of the CHD because, in certain embodiments, the CHD isprotected by two levels of obscurity. A user attempting to access theCHD may be required to authenticate with the tokenization providersystem and provide the authorization factor. Further, the authorizationfactor can be associated with the CHD and the user thereby preventing auser who is authorized to access the tokenization provider system, butnot the CHD from accessing the CHD.

Many variations of these example systems and associated processes aredescribed below in more detail with reference to the drawings. Further,in some cases, one or more of the various embodiments and systems can becombined into fewer embodiments or systems or split into multipleembodiments or systems.

Example Token-Sharing Environment

FIG. 1 illustrates an example embodiment of a token-sharing environment100. The token-sharing environment 100 can comprise a tokenizationprovider system 102, a merchant environment 104, and a third-partymerchant environment 106.

The tokenization provider system 102 is associated with a tokenizationprovider (not shown) and can generally include any system capable ofcreating a token associated with CHD, storing the token and the CHD, andproviding the token to a user (e.g. a merchant 142) of the tokenizationprovider system 102. Further, the tokenization provider system 102 cangenerally include any system capable of performing a payment cardtransaction on behalf of the merchant 142 without the merchant 142having or maintaining a copy of the CHD. This CHD can include anyinformation associated with a customer of the merchant environment 104and the customer's payment card that is necessary to process a paymenttransaction, but which the merchant 142 does not wish to store at themerchant environment 104 due to, for example, security-related expensesor concerns. Further, the payment card can be any type of card that canfacilitate completing the payment transaction. For example, the paymentcard can be a credit card, debit card, or gift card. One example of sucha tokenization provider system is the Dollars On The Net® solution fromShift4® Corporation of Las Vegas, Nev.

The merchant environment 104 can generally include any product orservice provider that accepts credit cards, or other types of paymentcards, for payment and utilizes the tokenization provider system 102 forpayment processing. For example, the merchant environment 104 can be ahotel, an electronics store, a restaurant, an online ecommerce website,or a healthcare provider, to name a few. Further, the merchantenvironment 104 may be associated with an organization, or merchantorganization, that is affiliated with or owns one or more merchantenvironments. For example, assuming the merchant environment representsa hotel, the organization may be associated with a number of hotellocations and/or hotel chains.

Generally, the merchant organization is a different organization thanthe tokenization provider. However, in some embodiments, the merchantorganization may be the same organization as the tokenization providerthat is associated with the tokenization provider system 102. Forexample, the tokenization provider system 102 may represent, at least inpart, the corporate headquarters for the merchant organization or it mayrepresent a central processing facility for processing paymenttransactions for one or more locations of the merchant environment 104.Further, the merchant environment 104 may represent a store locationowned by the merchant organization, or the merchant environment 104 mayrepresent a franchisee.

In one embodiment, the merchant environment 104 includes a merchant 142and an administrator 148. The merchant 142 can represent any individual(e.g. an employee) affiliated with the merchant environment 104 who mayor may not have administrative access to an account associated with thetokenization provider system 102. The admin 148 can represent anyindividual affiliated with the merchant environment 104 who hasadministrative access to an account associated with the tokenizationprovider system 102. For example, the admin 148 can be a manager or anowner of the merchant environment 104.

The third-party merchant environment 106 can generally include anyproduct or service provider that accepts credit cards, or other types ofpayment cards, for payment and may or may not utilize the tokenizationprovider system 102 for payment processing. For example, the third-partymerchant environment 106 can be a flower shop, a hotel, a theatre,another ecommerce website, or a franchisee of the merchant environment104. In one embodiment, the third-party merchant environment 106 mayutilize a tokenization provider system that is not affiliated with thetokenization provider system 102. In one embodiment, the third-partymerchant environment 106 includes a third-party merchant 162. Thethird-party merchant 162 can represent any individual associated withthe third-party merchant environment 106.

In one embodiment, the merchant 142 can obtain CHD from a customer (notshown) during a first or initial transaction. When the merchant 142provides the CHD to the POS 144, the POS 144 can provide the CHD to atoken access system 122, which is associated with the tokenizationprovider system 102. In turn, the token access system 122 can providethe POS 144 with a token associated with the CHD. This token can begenerated by the token access system 122 or a token generation system(not shown) that is associated with the tokenization provider system102. The POS 144 can then delete any CHD and can store the token at thetoken repository 152, which is part of the merchant repository system150. Further, the POS 144 can associate the token with a customerprofile associated with the customer and stored at the customer profilerepository 154, which is part of the merchant repository system 150. Thetoken access system 122 can store the CHD and the token, as well as therelationship between the token and the CHD, at the token/CHDrelationship repository 132, which is part of the tokenization providerrepository system 130.

The POS 144 can generally represent any point-of-sale system that canprocess payment card transactions by communicating with the credit cardprocessors 172, or by communicating with the tokenization providersystem 102, which communicates with the credit card processors 172 forthe POS 144. The tokenization provider system 102 may communicate withthe credit card processors 172 using, for example, the gateway 126. Inone embodiment, the POS 144 communicates directly with the tokenizationprovider system 102 via a private secure connection. Alternatively, thePOS 144 can communicate with the tokenization provider system 102 viathe network 170. The network 170 can include any type of wired orwireless network. For example, the network 170 can be a LAN, WAN, or theInternet, to name a few. The credit card processors 172 and the creditcard processor 174 can generally include any payment card processingsystem or service.

The token access system 122 can generally include any system that cangenerate tokens associated with CHD and provide the tokens to a merchantenvironment 104. Further, the token access system 122 can include anysystem that can regulate access to the tokens, and CHD associated withthe tokens.

The merchant repository system 150 can generally include any repository,database, or information storage system that can store informationassociated with the merchant environment 104. In one embodiment, themerchant repository system 150 comprises the token repository 152 andthe customer profile repository 154. The token repository 152 cangenerally include any system capable of storing tokens associated withCHD. In one embodiment, the token repository 152 stores tokenidentifiers associated with tokens stored at the tokenization providersystem 102. The customer profile repository 154 can generally includeany information associated with customers of the merchant environment104 that the merchant environment 104 may store. For example, thecustomer profile repository may include the customer's identity, thecustomer's preferences (e.g. red flowers or a corner hotel room), andthe customer's purchase history, to name a few. In one embodiment, oneor more of the token repository 152 and the customer profile repository154 may store information linking an entry in the customer profilerepository 154 with an entry in the token repository 152 therebyassociating a token with a customer. In one embodiment, the tokenrepository 152 and the customer profile repository 154 can be combinedor divided further.

The tokenization provider repository system 130 can generally includeany repository, database, or information storage system that can storeinformation associated with the tokenization provider system 102. In oneembodiment, the tokenization provider repository system 130 comprises atoken/CHD relationship repository 132, a token access repository 134,and a CHD access log repository 136. The token/CHD relationshiprepository 132 can generally include any system that can store CHD andtokens, as well as the relationship between the tokens and the CHD. Thetoken access repository 134 can generally include any system that canstore information associated with identifying who can access the tokensand CHD maintained by the tokenization provider system 102. Thisinformation can include user identification information, userauthentication information, and user/token relationship information, toname a few. The CHD access log repository 136 can generally include anysystem that can store information associated with token and CHD accessby users of the tokenization provider system 102. These users caninclude both users who use the tokenization provider system 102 fortokenization services (e.g. the merchant 142) and users who access thetokenization provider system 102 to access shared tokens or CHD (e.g.the third-party merchant 162). In one embodiment, the token/CHDrelationship repository 132, the token access repository 134, and theCHD access log repository 136 can be combined or divided further.

In one embodiment, the merchant 142 can provide the third-party merchant162 with access to the CHD. Providing the third-party merchant 162 withaccess to the CHD comprises the merchant 142 providing the third-partymerchant 162 with access to the token associated with the CHD. Toprovide the third-party merchant 162 with access to the CHD, themerchant 142 can send the token or token identifier and a merchantidentifier associated with the third-party merchant 162 to the tokenaccess system 122. Further, the token access system 122 provides thetoken or a token-identifier to the third-party merchant 162 enabling thethird-party merchant 162 to access the CHD associated with the token atthe tokenization provider system 102.

In one embodiment, the merchant 142 provides the token or thetoken-identifier to the third-party merchant 162 using, for example, thecomputing system 146 thereby enabling the third-party merchant 162 toaccess CHD associated with the token at the tokenization provider system102.

In one embodiment, access to the CHD is generally on a limited basis.For example, using the token, the third-party merchant 162 may only beable to access the CHD once, a small number of times, or for apredefined period (such as 15-minutes). However, access to the CHD isnot so limited in other embodiments.

In one embodiment, the merchant 142 can remove access to the CHD fromthe third-party merchant 162 by requesting that the token access system122 disassociate the token from the third-party merchant 162.

In some embodiments, the merchant 142 provides token access to one ormore users that have been pre-identified to the tokenization providersystem 102 by the admin 148 using, for example, the computing system146. Similarly, in some embodiments, the admin 148 can remove access tothe CHD from the one or more pre-identified users. In one embodiment,the pre-identified users can be third-parties (e.g. the third-partymerchant 162) and/or users associated with the merchant environment 104(e.g. the merchant 142).

In some embodiments, although the third-party merchant 162 may or maynot be a customer of the tokenization provider, to access the CHD, thethird-party merchant 162 registers with the token access system 122.Registration with the token access system 122 enables the token-accesssystem 122 to associate the token with the third-party merchant 162.Further, the registration enables the tokenization provider tooptionally verify the identity of the third-party merchant 162 and todetermine if the third-party merchant 162 is trustworthy based onpublicly available information or any other information source availableto the tokenization provider.

In one embodiment, the third-party merchant 162 accesses the tokenaccess system 122 via a computing system 164 or a POS 166. Thethird-party merchant 162 authenticates with the token access system 122and can then request the CHD associated with a token by providing a copyof the token or a token identifier associated with the token to a CHDaccess system 124. If the third-party merchant 162 has beenpre-authorized by the admin 148 to access the CHD, the CHD access system124 can provide the third-party merchant 162 with access to the CHD.Once the third-party merchant 162 has gained access to the CHD, thethird-party merchant 162 can process a transaction for the customer viathe POS 166 using the CHD. Alternatively, if the third-party merchant162 is a customer of the tokenization provider, the third-party merchant162 can use the gateway 126 to process the transaction. In oneembodiment, gaining access to the CHD enables the third-party merchant162 to view the CHD. Alternatively, in some embodiments, gaining accessto the CHD enables the third-party merchant 162 to perform a transactionwith or without viewing the CHD.

In one embodiment, the CHD access system 124 causes the CHD to bedisplayed to the user via one or more of the POS 166 and the computingsystem 164.

The CHD access system 124 can generally include any system that canprovide access to CHD associated with a token. In one embodiment, theCHD access system 124 authenticates a user and determines whether theuser is authorized to access the CHD before providing access to CHDassociated with a token.

The token access system 122, or the CHD access system 124, can log eachaccess of the CHD or token at the CHD access log repository 136, whichis part of the tokenization provider repository system 130.Advantageously, in some embodiments, by logging each access of the CHDor token, it can be determined if a potential unauthorized use of theCHD is attributable to the merchant 142, the third-party merchant 162,or some unrelated party.

The POS 166 can generally represent any point-of-sale system that canprocess payment card transactions by communicating with the credit cardprocessor 174. In one embodiment, the POS 166 communicates directly withthe credit card processor 174. Alternatively, the POS 166 communicateswith the credit card processor 174 via the network 170. The POS 166 mayalso communicate with the credit card processor 174 or the credit cardprocessors 172 using the tokenization provider system 102. Generally,this communication may occur if the third-party merchant environment 106is also a customer of the tokenization provider system 102. However, insome instances, the POS 166 may use the tokenization provider system 102to communicate with the credit card processors without the third-partymerchant environment 106 being a customer of the tokenization providersystem 102. For example, in some cases the third-party merchant 106 maybe authorized to use the tokenization provider system 102 wheninitiating transactions that use CHD associated with a token provided bya party that is a customer of the tokenization provider system 102, suchas the merchant environment 104. In one embodiment, the POS 166 and thePOS 144 can be similarly configured.

The gateway 126 can generally include any system that can processtransactions by providing CHD and transaction information to the creditcard processors 172 either directly or via the network 170 on behalf ofthe merchant environment 104.

The computing systems 146 and 164 can generally include any computingdevice(s), such as desktops, laptops, and wireless mobile devices (e.g.smart phones, PDAs, tablets, or the like), to name a few. In oneembodiment, one or more of the merchant environment 104 and thethird-party merchant environment 106 is associated with an ecommercewebsite. In one embodiment, the computing systems 146 and 164 can alsoinclude video game platforms, television set-top boxes, televisions(e.g., internet TVs), and computerized appliances, to name a few. In oneembodiment, the computing systems 146 and 164 can include any computingdevice that can interact with the tokenization provider system 102.

In one embodiment, providing access to a token and the CHD associatedwith the token comprises associating an authorization factor with thetoken. For example, to provide the third-party merchant 162 with accessto the CHD, the merchant 142 can send the token and a merchantidentifier associated with the third-party merchant 162 to the tokenaccess system 122. The token access system 122 can use the authorizationfactor generator 128 to generate an authorization factor. Theauthorization factor can be associated with the token and the merchantidentifier at the token access repository 134. The token access system122 can provide the authorization factor along with the token ortoken-identifier to the third-party merchant 162 enabling thethird-party merchant 162 to access the CHD associated with the token atthe tokenization provider system 102. In one embodiment, the merchant142 provides the authorization factor to the third-party merchant 162.

The authorization factor generator 128 can generally include any systemcapable of generating or otherwise accessing an authorization factor.The authorization factor can include any factor that can be used to helpauthenticate the third-party merchant 162 and to prevent automatedsystems, possibly associated with malicious users, from attempting toobtain CHD access. For example, the authorization factor can comprise aset of one or more random or pseudo-random words, numbers, symbols,images, sounds, or a combination of the same. In some embodiments, theauthorization factor can be non-random and may be associated with adefined algorithm. Further, in some embodiments, the authorizationfactor can be associated with a theme. For example, the authorizationfactor can be a set of four random color words, car images, or rockmusic sound bites. In some embodiments, the authorization factor can bea security question.

In one embodiment, to access CHD associated with a token, thethird-party merchant 162 authenticates with the tokenization providersystem 102. The third-party merchant 162 also provides both a token ortoken identifier and an authorization factor. If the authorizationfactor matches an authorization factor associated with the token and thetoken is associated with the third-party merchant 162, then the CHDaccess system 124 can provide the third-party merchant 162 with accessto the CHD associated with the token. Thus, in some embodiments, thethird-party merchant 162 must be registered with the tokenizationprovider system 102, and have been granted access to the CHD by themerchant 142.

In one embodiment, the admin 148 identifies the merchants, or users, tothe tokenization provider system 102 that the merchant 142 canpotentially provide token access. In one embodiment, the admin 148identifies to the tokenization provider system 102 the employees of themerchant environment 104 that can share token access with othermerchants, or users.

In one embodiment, the authorization factor is presented to thethird-party merchant 162 via a human-detection test, such as a captcha,reverse Turing test, or other challenge-response test. In oneembodiment, the authorization factor is presented to the third-partymerchant via a RSA hardware authenticator. In one embodiment, afterproviding the authorization factor, a phone-verification system (notshown) associated with the tokenization provider system 102 can contactthe third-party merchant 162 to request verification that thethird-party merchant 162 is attempting to access the CHD associated witha token. In some embodiments, use of the phone-verification system canadvantageously prevent attempts at automated CHD access by maliciousprograms.

In one embodiment, one or more of the token access system 122, the CHDaccess system 124, and the authorization factor generator 128 can belocated at the merchant environment 104.

As one example, non-limiting, use-case of an embodiment of the presentdisclosure, assume that the merchant environment 104 represents anelectronics store and the third-party merchant environment 106represents an extended warranty provider. The extended warranty provideris contracted with the merchant environment 104 to provide extendedwarranties to customers of the merchant environment 104 who opt topurchase an extended warranty with their electronic purchase. A customerwho is attempting to purchase a television may provide CHD to themerchant environment 104. The merchant environment 104 may then providethe CHD to the tokenization provider system 102. The tokenizationprovider system 102 processes the transaction and returns a tokenassociated with the CHD to the merchant environment 104 which stores thetoken and associates the token with the customer. Now, assume thecustomer decides to purchase the extended warranty for the television.The merchant environment 104 can authorize the third-party merchantenvironment 106 to use the token. The third-party merchant environment106 can then access the tokenization provider system 102 and request theCHD associated with the token, thereby enabling the third-party merchant106 to process the extended warranty transaction for the customer.Alternatively, the third-party merchant environment 106 can request thatthe tokenization provider system 102 process the extended warrantytransaction using the CHD associated with the token.

Example Token Provisioning Process

FIG. 2 illustrates a flow diagram for an example embodiment of a tokenprovisioning process 200. The process 200 can be implemented by anysystem that can generate and associate a token with CHD on behalf of amerchant 142 and can provide a second merchant, such as the third-partymerchant 162, with access to the token. For example, the process 200, inwhole or in part, can be implemented by one or more of the token accesssystem 122, the CHD access system 124, and the gateway 126. In oneembodiment, the second merchant can be a merchant that is associatedwith the merchant 142, such as an employee of the merchant 142. Althoughany number of systems, in whole or in part, can implement the process200, to simplify discussion, the process 200 will be described as beinggenerally implemented by the token access system 122.

The process 200 begins at block 202, where, for example, the tokenaccess system 122 receives CHD from the merchant 142. At block 204, thetoken access system 122 generates a token. This token can be any pieceof random or pseudo-random globally unique data that can be stored bythe merchant 142 in place of the CHD. In one embodiment, the token caninclude alphanumeric characters, symbols, pictures, etc. Generally,there exists no correlation between the token value or contents and thecontents of the CHD thereby making it impossible to determine the CHDfrom the token itself. However, in some embodiments, one or more piecesof the CHD can be used to facilitate generating the token. In oneembodiment, the token differs from an encrypted version of the CHD andthus, cannot be manipulated to obtain the CHD. In one embodiment, thetoken can be an encrypted form of the CHD or a combination of encryptedCHD and false non-CHD.

At block 206, the token access system 122 associates the token with theCHD. In some embodiments, the relationship between the token and the CHDis stored at the token/CHD relationship repository 132. In someembodiments, the token access system 122 may also associate the tokenwith the merchant 142. This relationship may also optionally be storedat the token/CHD relationship repository 132. In some cases, there mayexist a number of tokens and sets of CHD data. For example, there may beone, a hundred, a thousand, ten-thousand, a million, or more tokens andsets of CHD data. Thus, the token access system 122, for example, maymaintain relationships between a number of tokens and sets of CHD data,including, one, a hundred, a thousand, ten-thousand, etc. Generally, onetoken is associated with one set of CHD data. However, in someembodiments, a token may be associated with multiple sets of CHD dataand/or a set of CHD data may be associated with multiple tokens. Forexample, multiple merchants may have obtained a set of CHD from acustomer, and as a result, if more than one of the merchants usestokenization, it is possible for multiple tokens to be associated withone set of CHD.

At block 208, the token access system 122 provides the token to themerchant 142. In one embodiment, providing the token to the merchant 142enables the merchant to perform transactions without the CHD. Themerchant 142 can identify the token and provide transaction details, forexample, to the gateway 126 or the token access system 122. The gateway126 can then process the transaction on behalf of the merchant 142. Insome embodiments, the merchant 142 can store the token at the tokenrepository 152. Advantageously, in some embodiments, once the CHD hasinitially been provided to the token access system 122, the merchant 142can perform a transaction using the CHD without directly accessing,viewing, or maintaining a copy of the CHD at the merchant environment104.

At block 210, the token access system 122 receives a request toassociate the token with a second merchant, such as the third-partymerchant 162. In some embodiments, the request comprises receiving oneor more of an identifier, contact information, and account informationassociated with the third-party merchant 162. Generally, thisinformation does not include information that the third-party merchant162 uses to access the tokenization provider system 102. For example,the identifier or account information may include a public identifierthat the third-party merchant 162 can share with merchants who wish togrant the third-party merchant 162 with token access, but generally thepublic identifier is distinct from an identifier the third-partymerchant 162 uses to identify itself to the tokenization provider system162. However, in some embodiments, the public identifier and the loginidentifier may be the same. Further, in some embodiments, the requestcomprises receiving the identity of the token. Alternatively, therequest comprises receiving a copy of the token.

The token access system 122 authorizes the second merchant (e.g. thethird-party merchant 162) to access the token at block 212. In someembodiments, authorizing access to the token comprises authorizingaccess to the CHD. In some embodiments, block 212 can also compriseinforming the second merchant that the second merchant, or an accountassociated with the second merchant, is authorized to access the tokenand/or CHD. In some embodiments, informing the second merchant of theauthorization can comprise emailing, texting, leaving a voice message,or providing an alert via the POS 166, the computing system 164, or anaccount page associated with the third-party merchant 162 at thetokenization provider system 102. In some embodiments, authorizing thesecond merchant to access the token comprises providing a copy of thetoken and/or an identifier associated with the token to the secondmerchant. In some embodiments, the token access system 122 stores therelationship between the second merchant and the token and/or CHD at thetoken access repository 134.

Example Process for Accessing Cardholder Data

FIG. 3 illustrates a flow diagram for an example embodiment of a process300 for accessing cardholder data. The process 300 can be implemented byany system that can provide a second merchant, such as the third-partymerchant 162, with CHD associated with a token, which was created inresponse to a first merchant, such as the merchant 142, providing theCHD to the system or a related system. For example, the process 300, inwhole or in part, can be implemented by one or more of the token accesssystem 122, the CHD access system 124, and the gateway 126. In oneembodiment, the second merchant can be a merchant that is associatedwith the merchant 142, such as an employee of the merchant 142. In oneembodiment, the process 300 can be used by the merchant 142, whoinitially provided the CHD, or an employee of the merchant 142, toretrieve the CHD. Although any number of systems, in whole or in part,can implement the process 300, to simplify discussion, the process 300will be described as being generally implemented by the CHD accesssystem 124.

The process 300 begins at block 302, where, for example, the CHD accesssystem 124 receives user authentication information associated with, forexample, the third-party merchant 162. This user authenticationinformation can generally include any information that can be used toauthenticate the third-party merchant 162. For example, the userauthentication information can include: a user name, a password, a RSAtoken code (e.g. a code produced by an RSA SecurID™ hardwareauthenticator), and the response to a challenge-response test, such as ahuman-detection test response (e.g. a captcha response) or an answer toa security question.

At decision block 304, the CHD access system 124 determines, based atleast in part on the user authentication information, if the third-partymerchant 162 is authorized to access the tokenization provider system102, or any system associated with the tokenization provider system 102.If the third-party merchant 162 is not authorized to use thetokenization provider system 102, the CHD access system rejects thethird-party merchant 162 at block 306. In one embodiment, rejecting thethird-party merchant 162 can comprise initiating a registration processthat enables the third-party merchant 162 to register with thetokenization provider system 102. In one embodiment, rejecting thethird-party merchant 162 can comprise providing an error message to thethird-party merchant 162.

If the third-party merchant 162 is authorized to access the tokenizationprovider system 102, the CHD access system 124 receives a token from thethird-party merchant 162 at block 308. Alternatively, at block 308, theCHD access system 124 accesses the token pre-associated with thethird-party merchant 162 by the merchant 142 from the token accessrepository 134. In one embodiment, receiving the token comprisesreceiving a token identifier associated with the token. In oneembodiment, receiving the token includes receiving a request to accessCHD associated with the token.

At decision block 310, the CHD access system 124 determines if thethird-party merchant 162 is authorized to use the token. In oneembodiment, to determine if the third-party merchant 162 is authorizedto use the token, the CHD access system 124 determines if thethird-party merchant 162 is associated with the token at the tokenaccess repository 134.

If the third-party merchant 162 is not authorized to use the token, theCHD access system 124 rejects the third-party merchant's 162 request toaccess the CHD associated with the token at block 312. In oneembodiment, rejecting the third-party merchant's 162 request can includelogging the third-party merchant's 162 request at the CHD access logrepository 136. Further, in one embodiment, rejecting the third-partymerchant's 162 request can include informing the merchant 142 of thethird-party merchant's 162 attempt to use the token and/or access theCHD associated with the token. In one embodiment, in response to thethird-party merchant's 162 failed attempt to access the CHD, thetokenization provider system 102 can replace the token at thetokenization provider system 102 and the merchant environment 104 with anew token.

If the third-party merchant 162 is authorized to use the token, the CHDaccess system 124 provides access to CHD associated with the token atblock 314. In one embodiment, providing access to the CHD comprisesproviding the CHD to one or more of the POS 166 and the computing system164. In one embodiment, if given access to the CHD, the third-partymerchant 162 can view the CHD. Alternatively, the third-party merchant162 can initiate a transaction using the CHD at the POS 166, but withoutviewing the CHD. In one embodiment, providing access to the CHDcomprises the gateway 126 performing a transaction using the CHD onbehalf of the third-party merchant 162. In one embodiment, providing thethird-party merchant 162 with access to the CHD can include logging thethird-party merchant's 162 access of the CHD at the CHD access logrepository 136.

At block 316, the CHD access system 124 removes the third-partymerchant's 162 authorization to use the token, and consequently, thethird-party merchant's 162 authorization to access the CHD at thetokenization provider system 102. In one embodiment, removing thethird-party merchant's 162 authorization to use the token can comprisedisassociating the token and the third-party merchant 162 at the tokenaccess repository 134. In one embodiment, the threshold for removing thethird-party merchant's 162 authorization to use the token can be basedon any predetermined event. For example, authorization can be removedafter the third-party merchant 162 uses the token or accesses the CHD apre-determined number of times, such as once or five-times. As a secondexample, authorization can be removed after a pre-defined time period,such as 15-minutes from the time merchant 142 authorizes the third-partymerchant 162 to use the token, or 10-minutes from the time that thethird-party merchant 162 access the CHD using the token. In oneembodiment, block 316 is optional.

Second Example of a Token Provisioning Process

FIG. 4 illustrates a flow diagram for a second example embodiment of atoken provisioning process 400. The process 400 can be implemented byany system that can generate and associate a token with CHD on behalf ofa merchant 142 and can provide a second merchant, such as thethird-party merchant 162, with access to the token. For example, theprocess 400, in whole or in part, can be implemented by one or more ofthe token access system 122, the CHD access system 124, and the gateway126. In one embodiment, the second merchant can be a merchant that isassociated with the merchant 142, such as an employee of the merchant142. Although any number of systems, in whole or in part, can implementthe process 400, to simplify discussion, the process 400 will bedescribed as being generally implemented by the token access system 122.In some embodiments, the process 400 can be used to provide either athird-party merchant (e.g. the third-party merchant 162), or an employeeof the merchant 142 or the merchant environment 104 (e.g. the merchant142) with access to a token or CHD associated with the token. Tosimplify discussion, the process 400 will be described as being used toprovide the third-party merchant 162 with access to the token or CHDassociated with the token.

The process 400 begins at block 402, where, for example, the tokenaccess system 122 receives user authentication information associatedwith the merchant 142. This user authentication information can compriseany information necessary for the token access system 122 toauthenticate the merchant 142. For example, the user authenticationinformation can comprise a user name, a password, and a RSA token code,to name a few.

At decision block 404, the token access system 122 determines if themerchant 142 is authorized to grant a second merchant access to a token.In one embodiment, granting the second merchant access to the token caninclude granting the second merchant the ability to use the token toprocess a transaction. In one embodiment, decision block 404 comprisesdetermining if the merchant 142 is authorized to access one or more ofthe tokenization provider system 102, the token access system 122 andthe gateway 126. In one embodiment, the merchant 142 may have access tothe tokenization provider system 102 without having permission to accessall of the systems associated with the tokenization provider system 102.For example, the merchant 142 may have access to the gateway 126enabling the merchant 142 to process transactions for a customer, butmay not have access to the token access system 122 thereby preventingthe merchant 142 from providing token access to a second merchant. Inone embodiment, the admin 148 determines the merchant's 142 level ofaccess to the tokenization provider system 102. The admin 148 canconfigure an account associated with the merchant 142 and thetokenization provider system 102 to restrict the merchant's 142 level ofaccess to one or more of systems, tokens, and CHD associated with thetokenization provider system 102.

If the merchant 142 is not authorized to grant a second merchant accessto a token, the token access system 122 rejects the merchant 142 fromfurther accessing the token access system 122 at block 406. If themerchant 142 is authorized to grant token access to a second merchant,the token access system 122 receives the identity of a token from themerchant 142 at block 408. Receiving the identity of the token cancomprise receiving a token or receiving a token identifier associatedwith the token. Further, receiving the identity of the token may includereceiving a customer record that is associated with a token.Advantageously, in some embodiments, by providing a customer record (orportion thereof, such as a customer record identifier) that isassociated with a token to the token access system 122, the merchant 142can grant token access without knowing the token value, knowing that atoken exists, or having any understanding of how tokenization works.

In one embodiment, the token access system 122 verifies that themerchant 142 provided a token associated with the merchant 142 or themerchant environment 104. If the token is not associated with themerchant 142 or the merchant environment 104, the token access systemcan reject the token. In one embodiment, the token access system 122 canalso lock the merchant 142 out of the tokenization provider system 102,log the merchant's 142 actions at the CHD access log repository 130,report the access attempt to the admin 148, or combinations of the same.

At block 410, the token access system 122 receives the identity of thethird-party merchant 162, the user whom the merchant 142 wishes to granttoken access. In some embodiments, the token access system 122 receivesthe identity of the third-party merchant environment 106 or anorganization associated with the third-party merchant environment 106.In one embodiment, receiving the identity of the third-party merchant162 comprises receiving the identity of a merchant account associatedwith the tokenization provider system 102 and the third-party merchant162. As previously described, the identity can include any informationthat identifies the third-party merchant 162, or third-party merchantenvironment 106, to the tokenization provider system 102. This caninclude, for example, a unique identifier selected by the tokenizationprovider system 102 or the third-party merchant 162. As additionalexamples, the identifying information may include an e-mail address, aphone number, or any other contact information. Advantageously, in someembodiments, providing contact information as an identifier enables themerchant 142 to identify a third-party merchant 162 that has not yetregistered with the tokenization provider system 102 or without knowingthe third-party merchant's 162 unique identifier.

The token access system 122 may also receive a time-based or event-basedset of conditions associated with the third-party merchant 162 thatlimits the third-party merchant's 162 access to the CHD. For example,the conditions may limit the time-period in which the third-partymerchant 162 can access the CHD or the number of times the third-partymerchant 162 can access the CHD using the token. Further, in embodimentswhere the tokenization provider system 102 provides CHD access byperforming transactions on behalf of the third-party merchant 162, theconditions can include a monetary limit. Advantageously, in someembodiments, setting a monetary limit can prevent a third-party merchant162 from quoting one price to a customer or merchant 142 while charginga higher price once access to the CHD is obtained. The admin 148 mayalso pre-define the set of conditions such that each time the merchant142 provides a third-party merchant with CHD access, the set ofconditions are automatically associated with the CHD access.

At decision block 412, the token access system 122 determines if thethird-party merchant 162 is authorized to access tokens. Thisdetermination can comprise determining if the third-party merchant 162is registered with the tokenization provider system 102 and/or if thethird-party merchant 162 is authorized to access tokens associated withthe merchant environment 104. If the third-party merchant 162 is notauthorized to access tokens, the token access system 122 rejects themerchant selection of the third-party merchant 162 at block 414. In someembodiments, rejecting the merchant selection can comprise sending aregistration request to or initiating a registration process with thethird-party merchant 162. In some embodiments, rejecting the merchantselection can comprise requesting that the admin 148 authorize thethird-party merchant 162 to access tokens associated with the merchantenvironment 104, if so desired.

If the third-party merchant 162 is authorized to access tokens, thetoken access system 122 generates a set of random words at block 416using, for example, the authorization factor generator 128.Alternatively, the token access system 122 can generate any other typeof authentication factor using, for example, the authorization factorgenerator 128, as described above with respect to FIG. 1. At block 418,the set of random words are associated with the token identified atblock 408. At block 420, the set of random words are associated with thethird-party merchant 162. In one embodiment, the set of random words areassociated with a merchant account associated with the third-partymerchant environment 106. An employee associated with the third-partymerchant environment 106 that has access to the merchant account canthen use the set of random words and obtain access to the token andassociated CHD as described with respect to FIG. 5.

At block 422, the set of random words are provided to the third-partymerchant 162. In one embodiment, the set of random words can be providedby any type of communication. For example, the token access system 122can provide the set or random words by email, text, or voicemail, toname a few. In one embodiment, the set of random words are provided tothe merchant 142. The merchant 142 can then provide the set of randomwords to the third-party merchant 162. In one embodiment, performingblock 422 can further comprise performing block 212 as described withrespect to FIG. 2.

In one embodiment, the set of random words are provided in an encryptedformat to the third-party merchant 162. The third-party merchant 162 canthen decrypt the encrypted set of random words. In one embodiment, theset of random words can be provided in clear text. However, in someembodiments, because the set of random words are associated with thethird-party merchant 162, or the merchant account, at the tokenizationprovider system 102, malicious users are prevented from using the set ofrandom words to access the token and/or CHD associated with the token.

Second Example Process for Accessing Cardholder Data

FIG. 5 illustrates a flow diagram for a second example embodiment of aprocess 500 for accessing cardholder data. The process 500 can beimplemented by any system that can provide a second merchant, such asthe third-party merchant 162, with CHD associated with a token, whichwas created in response to a first merchant, such as the merchant 142,providing the CHD to the system or a related system. For example, theprocess 500, in whole or in part, can be implemented by one or more ofthe token access system 122, the CHD access system 124, and the gateway126. In one embodiment, the second merchant can be a merchant that isassociated with the merchant 142, such as an employee of the merchant142. In one embodiment, the process 500 can be used by the merchant 142,who initially provided the CHD, or an employee of the merchant 142, toretrieve the CHD. Further, the process 500 can be used by thethird-party merchant 162 to access CHD from any number of merchants whohave authorized the third-party merchant 162 to use their tokens.Although any number of systems, in whole or in part, can implement theprocess 500, to simplify discussion, the process 500 will be describedas being generally implemented by the CHD access system 124.

The process 500 begins at block 502, where, for example, the CHD accesssystem 124 receives user authentication information associated with thethird-party merchant 162. This user authentication information cangenerally include any information that can be used to authenticate thethird-party merchant 162. For example, the user authenticationinformation can include: a user name, a password, a RSA token code, andthe response to a challenge-response test, such as a captcha response oran answer to a security question.

At decision block 504, the CHD access system 124 determines, based atleast in part on the user authentication information, if the third-partymerchant 162 is authorized to access the tokenization provider system102, or any system associated with the tokenization provider system 102.In one embodiment, decision block 504 can include determining if thethird-party merchant 162 is registered with the tokenization providersystem 102. In one embodiment, decision block 504 can includedetermining if the merchant 142, or the admin 148, has provided thethird-party merchant 162 with access to tokens associated with themerchant 142 or the merchant environment 104.

If the third-party merchant 162 is not authorized to use thetokenization provider system 102, the CHD access system rejects thethird-party merchant 162 at block 506. In one embodiment, rejecting thethird-party merchant 162 can comprise initiating a registration processthat enables the third-party merchant 162 to register with thetokenization provider system 102. In one embodiment, rejecting thethird-party merchant 162 can comprise providing an error message to thethird-party merchant 162.

If the third-party merchant 162 is authorized to access the tokenizationprovider system 102, the CHD access system 124 receives a set of wordsfrom the third-party merchant 162 at block 508. Alternatively, oradditionally, the CHD access system 124 receives any authorizationfactor generated by the authorization factor generator 128 and providedto the third-party merchant 162 as part of the implementation of theprocess 400.

At decision block 510, the CHD access system 124 determines if the setof words received from the third-party merchant 162 match a set ofrandom words associated with a token. In one embodiment, the third-partymerchant 162 also identifies the token. Alternatively, the CHD accesssystem 124 identifies the token by determining if there exists any tokenassociated with a set of random words that match the received set ofwords and if so, the CHD access system 124 determines if the third-partymerchant 162 is authorized to access that token.

If the set of words received from the third-party merchant 162 do notmatch a set of random words associated with a token, the CHD accesssystem 124 rejects the third-party merchant 162 at block 506. Rejectingthe third-party merchant 162 can comprise causing an error message to bepresented to the third-party merchant 162. Further, in some embodiments,rejecting the third-party merchant 162 can cause an account associatedwith the third-party merchant 162 to be deactivated or suspended.

If the set of words received from the third-party merchant 162 matches aset of random words associated with a token, the CHD access system 124,at block 512, accesses the token associated with the set of random wordsat, for example, the tokenization provider repository system 130. Atblock 514, the CHD access system 124 obtains CHD associated with thetoken.

At block 516, the CHD access system 124 provides the third-partymerchant 162 with access to the CHD over a secure connection. In oneembodiment, the CHD is provided via the network 170. In one embodiment,the CHD is provided to the computing system 164 at block 516. Thecomputing system 164 can then provide the CHD directly to the POS 166and/or cause the CHD to be presented to the third-party merchant 162. Inone embodiment, the CHD is provided to the POS 166 at block 516. The POS166 can then provide the CHD to the credit card processor 174 tocomplete a transaction.

In one embodiment, providing the third-party merchant 162 with access tothe CHD can comprise the CHD access system 124 receiving transactioninformation associated with a requested transaction. The CHD accesssystem 124 can then provide the CHD and the transaction information tothe gateway 126, which can then process the transaction using the creditcard processors 172. Advantageously, in some embodiments, thethird-party merchant 162 is able to use the CHD without the CHD beingpresented to the third-party merchant 162. In one embodiment, a subsetof the CHD is presented to the third-party merchant 162 enabling thethird-party merchant 162 to log the transaction and/or to verify thatthe transaction is associated with the correct CHD or customer. In someembodiments, the CHD access system 124 may verify that the value of thetransaction does not exceed a pre-defined transaction-limit associatedwith the third-party merchant's 162 access of the CHD. If thetransaction-limit is exceeded, the CHD access system 124 can reject thetransaction. Further, the CHD access system 124 can report the attemptedtransaction to the merchant 142 or the admin 148. The CHD access system124 can also report successful transactions to the merchant 142 therebyenabling the merchant 142 to verify that the third-party merchant 162processed the transaction for the merchant's 142 customer.

In one embodiment, the CHD access system 124 logs each access and/orattempted access of the token and/or CHD at the CHD access logrepository 136. Advantageously, in some embodiments, if there is adisputed credit card use, the CHD access log repository 136 can beaccessed to determine what parties may have accessed the token and/orCHD around the time associated with the disputed credit card use.

At block 518, the CHD access system 124 disassociates the set of randomwords from the token and the third-party merchant 162. In oneembodiment, disassociating the set of random words can include deletingor removing the words from the tokenization provider system 102. In oneembodiment, block 518 is performed in response to the third-partymerchant 162 accessing the token and/or CHD. In one embodiment, block518 is performed in response to a pre-defined event. This pre-definedevent can include any event associated with the token and/or CHD. Forexample, the pre-defined event can comprise: the number of times the setof random words have been provided by the third-party merchant 162 tothe tokenization provider system 102 (e.g. once, or five times); thelength of time since the set of random words were associated with thetoken (e.g. 15-minutes); or the length of time since the third-partymerchant 162 first accessed the token and/or CHD, to name a few.

Further, in some embodiments, the CHD access system 124 may disassociatethe set of random words from the token without the third-party merchant162 having ever accessed or attempted to access the CHD. For example, ifthe pre-defined event is a time-limit or time-period, the CHD accesssystem 124 can disassociate the set of random words from the token atthe expiration of the time-limit or time-period whether or not thethird-party merchant 162 accessed the CHD. In addition, if the owner ofthe token (e.g. the merchant 142) ceases to trust the third-partymerchant 162, the token owner can access the tokenization providersystem 102 and remove the third-party merchant's 162 authorization toaccess the token, and thus the CHD associated with the token. Removingthe authorization to access the token may include disassociating the setof random words from the token prior to the pre-defined event occurring.

In one embodiment, the third-party merchant 162 can communicate with theCHD access system 124 using any secure system. For example, thethird-party merchant 162 can provide the user authentication informationor the set of random words using a secure portal or webpage associatedwith the tokenization provider system 102. Alternatively, thethird-party merchant 162 can use a virtual private network (VPN) or asecure application obtained from the tokenization provider system 102 toaccess the tokenization provider system 102 and to provide the userauthentication information or the set of random words to the CHD accesssystem 124.

Advantageously, in some embodiments, a merchant can use the process 200or 400 to reduce CHD misuse or the misappropriation of CHD by amalicious user because the CHD is not stored with the merchant. Further,in some embodiments, using the process 300 or 500, the merchant canprovide CHD to a third-party merchant who may not be a customer of thetokenization provider system or who may not be capable of interactingwith the tokenization provider system due to, for example, differing CHDprocessing systems or legal regulations in the third-party merchant'scountry or jurisdiction. Similarly, in some embodiments, the merchantcan use the process 300 or 500 to require CHD to complete a transactionwith a bank or credit card processor whose payment card processingsystems may not be capable of interacting with the tokenization providersystem.

Example Information Flow

FIG. 6 illustrates a flow diagram for an example flow 600 of informationusing a tokenization provider system 606. Some or all of the systemsdescribed herein can be used to facilitate the flow illustrated in FIG.6. For example, the interaction with the merchant 604 can be via acomputing system associated with the merchant 604. As a second example,interaction with the third-party merchant may be via a POS.

The flow 600 begins at event 1 with the customer 602 providing CHD tothe merchant 604. This CHD is then provided by the merchant 604 to thetokenization provider system 606 at event 2. At event 3, thetokenization provider system 606 generates a token and associates thetoken with the CHD. This token is provided to the merchant at event 4.Generally, but not necessarily, the merchant 604 can store the token inplace of the CHD and can destroy or not save any copies of the CHD thatthe merchant 604 received. In other embodiments, the merchant 604generates the token or at least a portion of the token instead of (or inaddition to) the tokenization provider system 606.

At event 5, the customer 602 provides a product or service request tothe merchant 604 for a product or service that may be provided by thethird-party merchant 608. For example, the request may be for operatickets, flowers, or for an appointment at a spa. At event 6, themerchant 604 authorizes the third-party merchant 608 to access the tokenat the tokenization provider system 606 by communicating theauthorization to the tokenization provider system 606. The tokenizationprovider system 606, at event 7, generates an authorization factor, suchas a set of four random words, and associates the third-party merchantwith the authorization factor and the token.

At event 8, the tokenization provider system 606 provides theauthorization factor to the merchant 604, such as by email or through aweb-portal. The merchant 604 provides the authorization factor and thecustomer's 602 product or service request to the third-party merchant608 at event 9. At event 10, the third-party merchant 608 authenticateswith the tokenization provider system 606. The third-party merchant 608also provides the authorization factor to the tokenization providersystem 606 at event 10. In some embodiments, authenticating andproviding the authorization factor may be two separate events.

Assuming that the third-party merchant 608 is authenticated and that thetokenization provider system 606 determines that the third-partymerchant 608 is authorized to access the token, the tokenizationprovider system 606 provides access to the CHD associated with the tokenat event 11. In some embodiments, providing access to the CHD mayinclude providing the CHD to the third-party merchant 608.

The flow of information illustrated in FIG. 6 is for illustrativepurposes and is not intended to be limiting. For example, in some cases,instead of, or in addition to, the tokenization provider system 606providing the authorization factor to the merchant 604 at event 8, thetokenization provider system 606 can provide the authorization factor tothe third-party merchant 608.

Examples of CHD Interface Screens

FIGS. 7-12 illustrate several non-limiting embodiments of interfacescreens that can be electronically generated by one or more of thetokenization provider system 102, the token access system 122, or anyother system that can regulate the access of CHD associated with atoken. Although the interface screens are illustrated as Graphical UserInterfaces (GUIs), the interface screens are not limited as such. Forexample, the interface screens can include command-line interfaces(CLIs), three-dimensional interfaces, or a combination of interfacetypes.

A user, such as the third-party merchant 162, can access the interfacescreens illustrated in FIGS. 7-12 using a POS 166, a computing system164, or the like. In some embodiments, some or all of the interfacescreens may be included as part of a web-based or Internet-basedsoftware application that is accessed via a network 170. Alternatively,some or all of the interface screens may be part of a client-sidesoftware application stored locally, such as on the computing system164, which can communicate over the network 170 with a server-sideapplication stored on, for example, the token access system 122.

FIG. 7 illustrates an embodiment of a user login interface 700. In someembodiments, the user login interface 700 enables a user (e.g. thethird-party merchant 162) who desires to access CHD associated withanother user's token (e.g. the merchant 142 or organization associatedwith the merchant 142) to access the token access system 122. In someembodiments, users who desire to provide token access to another party(e.g. a user or organization) can use the user login interface 700 toaccess the token access system 122. The third-party merchant 162 canprovide a user name and password using the login panel 702 toauthenticate with the token access system 122. Other authenticationmechanisms are possible. For example, the login panel 702 can presentthe third-party merchant 162 with an opportunity to present a uniquecryptographic identifier or key. This key, in certain embodiments, canthen be matched to or decrypted with a corresponding public key toauthenticate the third-party merchant 162.

The user login interface 700 includes a registration link 704. Thisregistration link 704 can be used to direct an unregistered user to aregistration screen, such as the user registration interface 800depicted in FIG. 8. Further, the user login interface 700 can alsoinclude a login link 706 that can be used to direct a user (e.g. themerchant 142) who is registered with the tokenization provider system102 to another login interface. This additional login interface can beuser by subscribers of the tokenization provider system 102 to managetoken access, such as to grant token access to third-party merchantorganizations and/or users.

FIG. 8 illustrates an embodiment of a user registration interface 800.The user registration interface 800 enables a user to register with thetoken access system 122 by providing, for example, contact information,a username, and a password. The user registration interface 800 can beused, for example, by the third-party merchant 162 of FIG. 1, who maynot necessarily be a customer of the provider of the tokenizationprovider system 102. By registering with the token access system 122, insome embodiments, the third-party merchant 162 can access CHD associatedwith tokens that have been associated with the third-party merchant 162or the third-party merchant environment 106 by the user who is acustomer of the organization associated with the tokenization providersystem 102.

In some embodiments, a merchant 142 or an organization associated withthe merchant environment 104 that is a customer of the organizationassociated with the tokenization provider system 102 can use the userregistration interface 800 to register an account with the token accesssystem 122. Advantageously, in certain embodiments, this enablesmerchants to share access to CHD and/or tokens with other merchantswhether or not the other merchants are customers of the tokenizationprovider system 102.

FIG. 9 illustrates an embodiment of a merchant selection interface 900.The merchant selection interface 900 enables a user (e.g. thethird-party merchant 162) to select or connect to another user orassociated organization (e.g. a merchant 142, a merchant environment104, or an organization associated with the merchant environment 104)that has provided token access to the user or an organization associatedwith the user (e.g. the user's employer). For example, the third-partymerchant 162 can use the merchant selection interface 900 to select theorganization associated with the merchant environment 104. In someembodiments, the third-party merchant 162 can select the merchantenvironment 104. For example, if the merchant organization is a hotelchain, the third-party merchant 162 can select a specific franchise,location, or branch of the hotel chain using the merchant selectioninterface 900.

In some embodiments, the merchant selection interface 900 enables thethird-party merchant 162 to select any organization (or user) registeredwith the tokenization provider system 102. Alternatively, the merchantselection interface 900 may be configured to enable the third-partymerchant 162 to select organizations (or users) that are currentlysharing a token with the third-party merchant 162. In some cases, thethird-party merchant 162 may be able to select any organization (oruser) that has shared a token with the third-party merchant 162 at somepoint, whether or not the organization is currently sharing a token withthe third-party merchant 162.

The merchant selection interface 900 can include an existing connectionspanel 902. The existing connections panel 902 can list some or all ofthe users or organizations with whom the third-party merchant 162 iscurrently connected. In some embodiments, the existing connections panel902 may list organizations that are sharing a token with the third-partymerchant 162. Alternatively, the existing connections panel 902 may listany organization with which the third-party merchant 162 has establisheda connection. In some embodiments, the third-party merchant 162 canselect organizations with which to connect. For some embodiments,organizations that are sharing tokens with the third-party merchant 162(or an associated organization) are automatically connected to thethird-party merchant 162 and may automatically be listed on the existingconnections panel 902.

The existing connections panel 902 can list connections in any order.For example, the existing connection panel 902 may list theorganizations that are currently sharing a connection before displayingother connections. Alternatively, for example, organizations may belisted in alphabetical order, by frequency of access, or based on whenthe organization was added to the list.

In some implementations, the merchant selection interface 900 caninclude one or more search fields 904 for locating organizations thatmay have shared a token with the third-party merchant 162 (or anassociated organization). These search fields 904 can include, forexample, a name field, a city field, an address field, or a product orservice field (e.g. electronics, hospitality, restaurants, etc.), toname a few. In some cases, the search fields 904 may be used to searchfor an organization that is known to the tokenization provider system102 or that has registered with the tokenization provider system 102.

The results list 906 can list the organizations identified based on theinformation supplied to the search fields 904. Although illustrated as adrop-down list, the results list 906 is not limited as such and mayinclude any type of GUI element, or other interface element, fordisplaying the list of results. For example, the results list 906 mayinclude a dialog box, pop-up dialog box, a combo box, or other GUIelement.

FIG. 10 illustrates an example embodiment of a populated merchantselection interface 1000. The populated merchant selection interface1000 is substantially similar to the merchant selection interface 900.However, the search fields 904 and the results list 906 of the populatedmerchant selection interface 1000 illustrate sample search informationand sample results respectively.

FIG. 11 illustrates an example embodiment of a CHD access interface1100. The CHD access interface 1100 enables the third-party merchant 162(or other user) to access CHD associated with a token that has beenshared with the third-party merchant 162 or an associated organizationof the third-party merchant 162. To access the CHD, in certainembodiments, the third-party merchant 162 can provide an authorizationfactor associated with the token that is associated with the CHD. As haspreviously been described, the authorization factor can be, for example,a set of four words. Further, the third-party merchant 162 can providethe authorization factor via authorization fields 1102. Authorizationfields 1102 can include any GUI element for providing the authorizationfactor including, for example, a GUI element that allows for theuploading of an authentication file, such as a cryptographic keyassociated with the third-party merchant 162. In the illustratedembodiment, the authorization fields 1102 include four text fields forentering the authorization factor.

The CHD access interface 1100 may also include a challenge-responsemechanism 1104. This challenge-response mechanism 1104 can include anymechanism for preventing automated systems, such as Internet bots, fromaccessing CHD using the CHD access interface 1100. For example, thechallenge-response mechanism can include a security question, aCompletely Automated Public Turing test to tell Computers and HumansApart (CAPTCHA) (as illustrated in FIG. 11), combinations of the same,or the like.

FIG. 12 illustrates an example of a CHD provisioning interface 1200. TheCHD provisioning interface 1200 can present CHD via CHD fields 1204 to auser, such as the third-party merchant 162. Further, the CHDprovisioning interface 1200 can include a timer 1202 that identifies howmuch time is remaining for the third-party merchant 162 to access theCHD before the CHD is cleared from the CHD provisioning interface 1200.

In some embodiments, the CHD provisioning interface 1200 includes GUIfields for specifying a transaction. Advantageously, in certainembodiments, the tokenization provider system 102 can perform thetransaction for the third-party merchant 162. Thus, in some embodiments,the CHD provisioning interface 1200 may not present the CHD to thethird-party merchant 162. However, the CHD provisioning interface 1200may present the status of the transaction, including a confirmationvalue.

TERMINOLOGY

A number of computing systems have been described throughout thisdisclosure. The descriptions of these systems are not intended to limitthe teachings or applicability of this disclosure. Further, theprocessing of the various components of the illustrated systems can bedistributed across multiple machines, networks, and other computingresources. For example, the token access system 122, the CHD accesssystem 124, and the authorization factor generator 128 can each beimplemented as separate servers or computing systems, or alternatively,as one server or computing system. In addition, two or more componentsof a system can be combined into fewer components. Further, variouscomponents of the illustrated systems can be implemented in one or morevirtual machines, rather than in dedicated computer hardware systems.Likewise, the data repositories shown can represent physical and/orlogical data storage, including, for example, storage area networks orother distributed storage systems. Moreover, in some embodiments theconnections between the components shown represent possible paths ofdata flow, rather than actual connections between hardware. While someexamples of possible connections are shown, any of the subset of thecomponents shown can communicate with any other subset of components invarious implementations.

Depending on the embodiment, certain acts, events, or functions of anyof the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out all together (e.g., not alldescribed acts or events are necessary for the practice of thealgorithms). Moreover, in certain embodiments, acts or events can beperformed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially. Although certaincomputer-implemented tasks are described as being performed by aparticular entity, other embodiments are possible in which these tasksare performed by a different entity.

Each of the various illustrated systems may be implemented as acomputing system that is programmed or configured to perform the variousfunctions described herein. The computing system may include multipledistinct computers or computing devices (e.g., physical servers,workstations, storage arrays, etc.) that communicate and interoperateover a network to perform the described functions. Each such computingdevice typically includes a processor (or multiple processors) thatexecutes program instructions or modules stored in a memory or othernon-transitory computer-readable storage medium. The various functionsdisclosed herein may be embodied in such program instructions, althoughsome or all of the disclosed functions may alternatively be implementedin application-specific circuitry (e.g., ASICs or FPGAs) of the computersystem. Where the computing system includes multiple computing devices,these devices may, but need not, be co-located. The results of thedisclosed methods and tasks may be persistently stored by transformingphysical storage devices, such as solid state memory chips and/ormagnetic disks, into a different state. Each service described, such asthose shown in FIG. 3, may be implemented by one or more computingdevices, such as one or more physical servers programmed with associatedserver code.

Conditional language used herein, such as, among others, “can,” “might,”“may,” “e.g.,” and the like, unless specifically stated otherwise, orotherwise understood within the context as used, is generally intendedto convey that certain embodiments include, while other embodiments donot include, certain features, elements and/or states. Thus, suchconditional language is not generally intended to imply that features,elements and/or states are in any way required for one or moreembodiments or that one or more embodiments necessarily include logicfor deciding, with or without author input or prompting, whether thesefeatures, elements and/or states are included or are to be performed inany particular embodiment.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it will beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As will berecognized, the processes described herein can be embodied within a formthat does not provide all of the features and benefits set forth herein,as some features can be used or practiced separately from others. Thescope of protection is defined by the appended claims rather than by theforegoing description. All changes which come within the meaning andrange of equivalency of the claims are to be embraced within theirscope.

1. (canceled)
 2. A method for sharing a token associated with cardholderdata in a tokenization provider system to enable the sharing ofcardholder data between users, the method comprising: by a token accesssystem implemented in a computing system comprising one or more hardwareprocessors: generating a first authorization factor; associating thefirst authorization factor with a token by storing a relationshipbetween the token and the CHD in physical computer memory, wherein thetoken is associated with cardholder data (CHD) in a tokenizationprovider system; associating, in the physical computer memory of thetoken access system, the first authorization factor with a user;providing the user with access to the first authorization factor;receiving user authentication information associated with the user;receiving a second authorization factor from the user; determiningwhether the user is authorized to use the token by at leastauthenticating the user based, at least in part, on the userauthentication information, and determining whether the secondauthorization factor matches the first authorization factor; and inresponse to determining that the user is authorized to use the token,providing the user with electronic access to the token; receiving atransaction request associated with a transaction using the CHD;performing the transaction on behalf of the user using the CHDcorresponding to the token without providing the user with access to theCHD; and in response to a triggering event, removing the user'sauthorization to access the token by disassociating the token from theuser in the physical computer memory.
 3. The method of claim 2, whereinthe first authorization factor and the second authorization factorcomprise one or more words.
 4. The method of claim 2, whereindetermining that the user is authorized to use the token furthercomprises determining whether the user is authorized to provide thesecond authorization factor.
 5. The method of claim 2, wherein providingaccess to the token further comprises providing access to the CHDassociated with the token.
 6. The method of claim 5, wherein providingaccess to the CHD further comprises retrieving the CHD from thetokenization provider system.
 7. The method of claim 5, whereinproviding access to the CHD further comprises authorizing the user toinitiate the transaction with the CHD.
 8. The method of claim 5, whereinproviding access to the CHD further comprises: accessing the transactionrequest associated with the user; and providing the token and thetransaction request to the tokenization provider system, wherein thetokenization provider system performs the transaction associated withthe transaction request.
 9. The method of claim 2, further comprisingdisassociating the first authorization factor with the token in responseto a predefined event.
 10. The method of claim 2, further comprisingregistering the user with the token access system.
 11. The method ofclaim 10, wherein associating the first authorization factor with theuser further comprises: determining if the user is registered with thetoken access system; determining if the user is authorized to accessauthorization factors; and in response to determining that the user isregistered with the token access system and is authorized to access theauthorization factors, associating the first authorization factor withthe user.
 12. The method of claim 2, further comprising maintaining arelationship between tokens and a number of sets of CHD for at least athousand users.
 13. The method of claim 2, wherein the triggering eventcomprises at least one of a received command; a number of accesses ofthe token; or a time period associated with access by the user of thetoken.
 14. The method of claim 2, wherein the first authorization factorand the second authorization factor comprise a number, an image, asound, or a challenge.
 15. The method of claim 2, wherein the CHD isreceived from a second user who obtains the CHD from a customer, thesecond user associated with a separate entity from an entity of theuser.
 16. A method for sharing a token at a third-party systemassociated with cardholder data to enable the sharing of access to thecardholder data between users, the method comprising: by a tokenizationprovider system comprising one or more hardware processors: receivingcardholder data (CHD) from a first user associated with a first entity;generating a token corresponding to the CHD; generating an authorizationfactor for the token and providing the first user with access to theauthorization factor; receiving a request from a second user to accessthe token, the second user associated with a second entity differingfrom the first entity, the request including an authorization factorinput; determining whether the second user is authorized to access thetoken by at least comparing the authorization factor input to theauthorization factor to determine whether the second user is authorizedto access the token; in response to determining that the second user isauthorized to access the token, providing the second user with access tothe token, wherein providing the second user with access to the tokencomprises performing a transaction using the CHD associated with thetoken on behalf of the user without providing the user with access tothe CHD; and in response to a triggering event, removing access to thetoken from the second user by disassociating the token with the seconduser.
 17. The method of claim 16, wherein the authorization factorcomprises a set of words that is associated with the token, the set ofwords unique to the token.
 18. The method of claim 16, furthercomprising authenticating the second user prior to receiving the requestfrom the second user to access the token.
 19. The method of claim 16,wherein determining whether the second user is authorized to access thetoken further comprises determining whether the first user hasauthorized the second user to access tokens associated with the firstuser.
 20. The method of claim 16, wherein the triggering event comprisesat least one of a received command; a number of accesses of the token;or a time period associated with access by the user of the token. 21.The method of claim 16, further comprising disassociating theauthorization factor from the token in response to the triggering event.